Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility #2

Merged
merged 2 commits into from
May 11, 2020
Merged

Accessibility #2

merged 2 commits into from
May 11, 2020

Conversation

dleadbetter
Copy link
Collaborator

This pull request adds the "a11y" addon to Storybook to support accessibility testing for Section 508 compliance. The addon displays an additional tab that lists elements that are not compliant with Section 508 standards:

Screen Shot 2020-05-11 at 1 50 03 PM

Some of the elements are indeed still failing, most due to an invalid color contract ratio. Since the components in this library are intended to be used in any number of projects, I think (but am open to suggestions) the accessibility changes should take place in the individual projects that required Section 508 compliance.

@dleadbetter dleadbetter requested a review from jamiefolsom May 11, 2020 17:53
Copy link
Member

@jamiefolsom jamiefolsom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree about allowing projects to implement their own solutions if necessary. If there are simple, global changes that would improve A11y throughout (like color or contrast, eg), it seems fine to me to implement those in the generic components.

@dleadbetter dleadbetter merged commit 71ec9b4 into master May 11, 2020
@dleadbetter dleadbetter deleted the feature/accessibility branch May 11, 2020 18:53
dleadbetter added a commit that referenced this pull request Jun 1, 2021
…cal_components

BASIRA #2 - Physical components
dleadbetter added a commit that referenced this pull request Aug 29, 2023
dleadbetter added a commit that referenced this pull request Aug 31, 2023
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 18, 2024
dleadbetter pushed a commit that referenced this pull request Mar 20, 2024
dleadbetter pushed a commit that referenced this pull request Mar 20, 2024
dleadbetter pushed a commit that referenced this pull request Mar 20, 2024
dleadbetter pushed a commit that referenced this pull request Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants